To clarify the below:

• Temporary places a Docker volume under your configured Apps dataset (avoid if that's on HDD)

When first setting up Apps section on SCALE, users have to select parent pool where the internal dataset for apps data will be created. So they should know what that is and where I hope...

EDIT: Actually screw it, I'll modify it to say where to check.

@nyanmisaka please review the HWA related items

I added forum post here with the question about tmpfs limits: https://forums.truenas.com/t/question-about-tmpfs-mount-for-apps-and-its-memory-limits-in-electric-eel/21473 (but it's a miniscule problem, so I wouldn't hold the whole PR just for this if we don't get a concrete answer)

Btw there's also more thorough instructions at TrueNAS docs themselves for Jellyfin: https://www.truenas.com/docs/truenasapps/communityapps/jellyfin/

We could consider linking them too somewhere at the end maybe? But it's worth noting that the screenshots are based on older TrueNAS release, so they're gonna be a bit outdated compared to ours now.

You don't need to force push with every change. We squash when merging.

Fair. Just a habit for situations where there's multiple logically separated commits potentially, but that's not really in docs repo I suppose

• fixed mention of swap, I learnt that since 24.04 swap is globally disabled by default
• changed wording to You may need to increase the limit if you have many media files streamed with transcoding at once, or transcodes might fail., since when you think about it, the size of your library doesn't really matter at all, what matters is how many people try to transcode at the same time and what kind of bitrate they're using (the latter largely boiling down to whether they stream from LAN or WAN since autodetection)

But now that I think about it, large media files might result in larger default bitrate selected and thus also more storage needed by default. Hmm, maybe I should re-add the "large" word then. Let me know if I should please, because I'm actually not sure how much the original file size influences the automatic bitrate...

As for the Docker memory usage limit, I got a response on the forums post:

We’ve had some internal discussion about it, but ultimately anything I say about the tmpfs behavior would be a guess. As you’ve seen, Docker docs aren’t very helpful on the subject and looking around online I’ve seen both things saying that the tmpfs mount is and is not limited by the overall container restrictions.

Since we’re passing through default docker behavior there, I think the best bet barring extensive testing is to reach out to the docker devs and try to get an answer from the source.

But Docker devs were kinda silent about it on the posts I found on their forums. So for now I'd just leave that cautious sentence there, and it could be revisited in case the problem comes up for someone and they'll find out empirically:

Note that total memory usage may also be capped in the Resources Configuration section.

Single large files and many small files at the same time can both cause problems with transcode directory filling up. so the large files should be added back.

Cloudflare Pages deployment